Skip to content

Conversation

@BaerMitUmlaut
Copy link
Contributor

Some S3 implementations do not include the XML namespace in their responses:

<?xml version="1.0" encoding="UTF-8"?>
<CopyObjectResult>
    <LastModified>
        2022-10-29T15:34:41.626Z
    </LastModified>
    <ETag>
        &#34;ead3fcd881dee32547f1b6ca1fc29463&#34;
    </ETag>
</CopyObjectResult>

minio-dotnet fails to deserialize such a response, this PR fixes that.

I encountered this issue in the wild, I'm guessing my provider uses seaweedfs, which has fixed this just hours ago: seaweedfs/seaweedfs#6676
However, they might not be the only ones with that behaviour.

@ebozduman
Copy link
Collaborator

@BaerMitUmlaut
I'd like to merge your commit.
I tried to rebase your fix-no-namespace branch so that the format/lint issues hit during the build process in UtilsTest.cs file can be fixed, but it did not work.
Please look into this issue. You may need to rebase your master first, I guess, and then rebase your fix-no-namespace branch, so that I can merge this PR.
Please let me know if you have any questions.

@BaerMitUmlaut
Copy link
Contributor Author

I think this should fix it, does not complain locally.

Copy link
Collaborator

@ebozduman ebozduman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ebozduman ebozduman merged commit ac5dc79 into minio:master Nov 5, 2025
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants